Maintaining snapshot and active file system metadata in an on-disk structure of a fle system

ABSTRACT

An on-disk structure of a file system has the capability to maintain snapshot and file system metadata on a storage system. The on-disk structure arranges file system data sequentially on disk within regions, wherein each region comprises a predetermined amount of disk space represented by blocks. The snapshot and file system metadata is maintained within level 1 (L1) indirect blocks of the on-disk structure. Each L1 indirect block describes (i.e., represents) a corresponding region of the on-disk structure of the file system; in the case of an active region, e.g., an L1 indirect block represents an active file data portion of a large file. The L1 indirect block that references an active region also performs file block number-to-disk block number mapping for the region.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is a Continuation of commonly assigned U.S. patent application Ser. No. 11/693,061, filed on Mar. 29, 2007, now issued as U.S. Pat. No. ______ on ______.

FIELD OF THE INVENTION

The present invention relates to file systems and, more specifically, to maintenance of snapshot and active file system metadata in an on-disk structure of a file system.

BACKGROUND OF THE INVENTION

A storage system is a computer that provides storage service relating to the organization of information on writable persistent storage devices, such as memories, tapes or disks. The storage system is commonly deployed within a storage area network (SAN) or a network attached storage (NAS) environment. When used within a NAS environment, the storage system may be embodied as a file server including an operating system that implements a file system to logically organize the information as a hierarchical structure of data containers, such as directories and files on, e.g., the disks. When used within a SAN environment, the storage system may organize the information in the form of databases or files. Where the information is organized as files, the client requesting the information typically maintains file mappings and manages file semantics, while its requests (and system responses) address the information in terms of block addressing on disk using, e.g., logical unit numbers.

Each “on-disk” file may be implemented as set of data structures, i.e., disk blocks, configured to store information, such as the actual data for the file. These data blocks are typically organized within a volume block number (vbn) space that is maintained by the file system. The file system may also assign each data block in the file a corresponding “file offset” or file block number (fbn). The file system typically assigns sequences of fbns on a per-file basis, whereas vbns are assigned over a larger volume address space. That is, the file system organizes the data blocks within the vbn space as a volume; each volume may be, although is not necessarily, associated with its own file system. The file system typically consists of a contiguous range of vbns from zero to n, for a file system of size n-1 blocks.

The storage system may be further configured to operate according to a client/server model of information delivery to thereby allow many clients to access files stored on the system. In this model, the client may comprise an application, such as a database application, executing on a computer that “connects” to the storage system over a computer network, such as a point-to-point link, shared local area network, wide area network or virtual private network implemented over a public network, such as the Internet. The client typically communicates with the storage system by exchanging discrete frames or packets of data according to pre-defined protocols, such as the Transmission Control Protocol/Internet Protocol (TCP/IP). In addition, the client may request the services of the system by issuing file system protocol messages over the network to the storage system.

A file system may have the capability to generate a snapshot of its active file system. An “active file system” is a file system to which data can be both written and read, or, more generally, an active store that responds to both read and write operations. The snapshot, i.e., snapshot data, refers to a copy of file system data that diverges from the active file system over time as the active file system is modified. Snapshots are well-known and described in TR3002 File System Design for a NFS File Server Appliance by David Hitz et al., published by Network Appliance, Inc. and in U.S. Pat. No. 5,819,292 entitled Method for Maintaining Consistent States of a File System and For Creating User-Accessible Read-Only Copies of a File System, by David Hitz et al., each of which is hereby incorporated by reference as though full set forth herein.

A common type of file system is a “write in-place” file system, where the locations of the data structures on disk are typically fixed. That is, the disk is “viewed” as a large sequential array of blocks and changes (updates) to the data of a file stored in the blocks are made in-place, i.e., data is overwritten at the same disk locations. The write in-place file system may assume a layout such that the data is substantially contiguously arranged on disks. This disk layout results in efficient access operations, particularly for sequential read operations, directed to the disks. Updating of data in-place thus maintains efficient read access to the data, but often at the expense of write performance.

Another type of file system is a journal or log-structured file system that generally does not overwrite data on disks. If a data block on disk is retrieved (read) from disk into memory of the storage system and changed or “dirtied” with new data provided by, e.g., an application, the data block is stored (written) to a new location on disk to optimize write performance. The file system typically uses block allocation data structures, such as an active map and one or more snapshot maps, to select free blocks within its vbn space to which to write the dirty blocks. As used herein, an active map denotes a file including a bitmap associated with a free status of the active file system. The snapshot map denotes a file including a bitmap associated with the vacancy of blocks of a snapshot. By examining the active and snapshot maps, the file system can determine whether a block is in use by either the active file system or any snapshot.

The block allocation data structures describe block usage within the file system and, as such, represent snapshot and file system metadata. As used herein, the term metadata denotes information used to describe, e.g., data containers, such as snapshots and files. In particular, the snapshot map data structures are used and maintained by the file system as existing infrastructure for the volume. However, the maintenance of such metadata within the block allocation structures may be expensive in terms of storage and access efficiencies.

SUMMARY OF THE INVENTION

The present invention overcomes the disadvantages of the prior art by providing an on-disk structure of a file system that has the capability to maintain snapshot and file system metadata on a storage system. The file system also has the capability to generate snapshots and provide fast sequential read access to data containers, such as snapshots and files. The on-disk structure arranges file system data sequentially on disk within regions, wherein each region comprises a predetermined amount of disk space represented by blocks. Notably, the on-disk structure accommodates a plurality of types of regions, including (i) active regions that contain active file system data for large files, (ii) snap-shot regions that contain snapshot data for the large files and (iii) metadata regions that contain metadata, as well as directories and small files.

According to the invention, snapshot and file system metadata for a region is maintained within level 1 (L1) indirect blocks of the on-disk structure. Each L1 indirect block describes (i.e., represents) a corresponding region of the on-disk structure of the file system; in the case of an active region, e.g., an L1 indirect block represents an active file data portion of a large file. The L1 indirect block that references an active region also enables file block number-to-disk block number mapping for the region. The L1 indirect block is illustratively stored as the initial (root) block of its corresponding region. Storage of the L1 indirect block within a corresponding region is advantageous because most read and write operations require access (load/store) of the indirect block. In addition, storage of the indirect block with the data of the region reduces disk head movement, thereby improving performance of the storage system. In sum, the L1 indirect block keeps track of essentially all “accounting” information for the region, including whether a previous location of block is in the snapshot and must be maintained, thereby obviating the need for additional block allocation data structures, such as snapshot maps.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and further advantages of the invention may be better understood by referring to the following description in conjunction with the accompanying drawings in which like reference numerals indicate identical or functionally similar elements:

FIG. 1 is a schematic block diagram of an environment including a storage system that may be advantageously used with the present invention;

FIG. 2 is a schematic block diagram of a storage operating system that may be advantageously used with the present invention;

FIG. 3 is a schematic block diagram illustrating an on-disk structure of a file system that may be advantageously used in accordance with the present invention;

FIG. 4 is a schematic block diagram illustrating an on-disk structure of a file that may be advantageously used in accordance with the present invention;

FIG. 5 is a schematic block diagram illustrating regions of disk space that may be advantageously used with the present invention;

FIG. 6 is a schematic diagram illustrating the organization of an active region that may be advantageously used with the present invention;

FIG. 7 is a schematic block diagram of the internal structure of a level 1 indirect block in accordance with the present invention; and

FIG. 8 is a schematic block diagram of an indirect block tree that may be advantageously used with the present invention.

DETAILED DESCRIPTION OF AN ILLUSTRATIVE EMBODIMENT

FIG. 1 is a schematic block diagram of an environment 100 including a storage system configured to provide storage services relating to the organization of information on writable persistent storage devices, such as disks 130. The storage system 120 is illustratively embodied as a computer comprising a processor 122, a memory 124, a network adapter 126 and a storage adapter 128 interconnected by a system bus 125. The storage system serves both file and block protocol access to information stored on the storage devices for users (system administrators) and clients of network attached storage (NAS) and storage area network (SAN) deployments. The storage system 120 provides NAS services through a file system and SAN services through SAN virtualization, including logical unit number (lun) emulation.

The memory 124 comprises storage locations that are addressable by the processor 122 and adapters 126, 128 for storing software programs and data structures associated with the embodiments described herein. The processor and adapters may, in turn, comprise processing elements and/or logic circuitry configured to execute the software programs and manipulate the data structures. A storage operating system 200, portions of which is typically resident in memory and executed by the processing elements, functionally organizes the storage system by, inter alia, invoking storage operations in support of software processes executing on the system. It will be apparent to those skilled in the art that other processing and memory means, including various computer readable media, may be used to store and execute program instructions pertaining to the invention described herein.

The network adapter 126 comprises the mechanical, electrical and signaling circuitry needed to connect the storage system 120 to a client 110 over a computer network 160, which may comprise a point-to-point connection or a shared medium, such as a local area network. The client 110 may be a general-purpose computer configured to execute applications 112, such as a database application. Moreover, the client 110 may interact with the storage system 120 in accordance with a client/server model of information delivery. To that end, the client may utilize file-based access protocols when accessing information (in the form of files) over a NAS-based network. In addition, the client 110 may utilize block-based access protocols, such as the Small Computer Systems Interface (SCSI) protocol, when accessing information (in the form of blocks, disks or luns) over a SAN-based network.

The storage adapter 128 cooperates with the storage operating system 200 executing on the storage system to access information requested by the client. The information may be stored on the disks 130 or other similar media adapted to store information. The storage adapter includes input/output (I/O) interface circuitry that couples to the disks over an I/O interconnect arrangement, such as a conventional high-performance, Fibre Channel (FC) serial link topology. The information is retrieved by the storage adapter and, if necessary, processed by the processor 122 (or the adapter 128) prior to being forwarded over the system bus 125 to the network adapter 126, where the information is formatted into one or more packets and returned to the client 110.

Storage of information on the storage system 120 is preferably implemented as one or more storage volumes 140 that comprise one or more disks 130 cooperating to define an overall logical arrangement of volume block number (vbn) space on the volume(s). Each volume 140 is generally, although not necessarily, associated with its own file system. The disks within a volume/file system are typically organized as one or more groups, wherein each group may be operated as a Redundant Array of Independent (or Inexpensive) Disks (RAID). Most RAID implementations, such as a RAID-4 level implementation, enhance the reliability/integrity of data storage through the redundant writing of data stripes across a given number of physical disks in the RAID group, and the appropriate storing of parity information with respect to the striped data. An illustrative example of a RAID implementation is a RAID-4 level implementation, although it should be understood that other types and levels of RAID implementations may be used in accordance with the inventive principles described herein.

To facilitate access to the disks 130, the storage operating system 200 implements a file system that logically organizes the information as a hierarchical structure of data containers, such volumes, files and luns, on the disks 130, to thereby provide an integrated NAS and SAN approach to storage by enabling file-based (NAS) access to the volumes and files, while further enabling block-based (SAN) access to the luns on a file-based storage platform. In an illustrative embodiment described herein, the storage operating system is the FreeBSD operating system kernel available from Network Appliance, Inc., Sunnyvale, Calif. that implements a Move Anywhere Proximate Layout (MAPL™) file system. However, it is expressly contemplated that any appropriate file system can be used, and as such, where the term “MAPL” is employed, it should be taken broadly to refer to any file system that is otherwise adaptable to the teachings of this invention.

A file system layout is provided that apportions an underlying physical volume into one or more flexible volumes (hereinafter “volumes”) of the storage system 120. The underlying physical volume is an aggregate 150 comprising one or more groups of disks, such as RAID groups. An example of such a file system layout is described in U.S. patent application Ser. No. 10/836,817 titled EXTENSION OF WRITE ANYWHERE FILE SYSTEM LAYOUT, by John K. Edwards et al. and assigned to Network Appliance, Inc., which is hereby incorporated by reference as though fully set forth herein.

As used herein, the term “storage operating system” generally refers to the computer-executable code operable on a computer to perform a storage function that manages data access and may, in the case of a storage system 120, implement data access semantics of a general purpose operating system. The storage operating system can also be implemented as a microkernel, an application program operating over a general-purpose operating system, such as UNIX® or Windows NT®, or as a general-purpose operating system with configurable functionality, which is configured for storage applications as described herein.

In addition, it will be understood to those skilled in the art that the invention described herein may apply to any type of special-purpose (e.g., file server, filer or storage serving appliance) or general-purpose computer, including a standalone computer or portion thereof, embodied as or including a storage system. Moreover, the teachings of this invention can be adapted to a variety of storage system architectures including, but not limited to, a network-attached storage environment, a storage area network, a disk assembly directly-attached to a client or host computer and a distributed architecture of network and disk element nodes organized as a storage system cluster. The term “storage system” should therefore be taken broadly to include such arrangements in addition to any subsystems configured to perform a storage function and associated with other equipment or systems.

FIG. 2 is a schematic block diagram of the storage operating system 200 that may be advantageously used with the present invention. The storage operating system comprises a series of software layers organized to form an integrated network protocol stack 210 that provides data paths for clients to access information stored on the storage system using block and file access protocols. The network protocol stack 210 illustratively includes a network driver layer (e.g., an Ethernet driver and a FC driver), a network protocol layer (e.g., an Internet Protocol layer and its supporting transport mechanisms, the Transport Control Protocol layer and the User Datagram Protocol layer), and a file/block protocol server layer (e.g., a Common Internet File System server, a Network File System server, an iSCSI server, etc.). In addition, the storage operating system includes a RAID system layer 220 that implements a disk storage protocol, such as a RAID protocol, and a storage driver layer 230 that implements a disk access protocol such as, e.g., a SCSI protocol.

Disposed between the network protocol stack 210 and RAID system 220 is a file system layer 300 that implements a file system, such as the MAPL file system. The file system 300 is illustratively a journal file system that is targeted to large file workloads and that has the capability to generate snapshots without the need to perform an expensive copy-on-write operation for every write operation directed to file system data, i.e., the file system is configured to perform such operations reasonably efficient. The file system 300 has an on-disk format representation that is block-based using index nodes (“inodes”) to identify files and file attributes (such as creation time, access permissions, size and block location). The file system also illustratively uses data structures to store metadata describing the layout of its file system; these metadata structures include, among others, an inode table.

An on-disk structure of the file system 300 provides fast sequential read access to data containers, such as files and snapshots. Illustratively, the file system apportions the storage space of storage devices, such as disks, into a plurality of regions and arranges the file system data sequentially on disk within the regions. Each region comprises a predetermined amount of disk space represented by blocks, e.g., disk blocks. A space allocation map identifies those regions that are allocated and those regions that are available (free) for allocation. The space allocation map is illustratively embodied as a bit map and is organized on a region (e.g., 1 MB or larger) granularity, e.g., the allocation map includes one bit per region. Accordingly, the file system 300 allocates entire regions of disk space, wherein the regions can be designated for different purposes/roles. Illustratively, the designated role of a region can be discerned through examination of certain Mode metadata (or alternatively via an identifier that indicates its role).

FIG. 3 is a schematic block diagram illustrating the on-disk structure of the file system 300 that may be advantageously used in accordance with the present invention. The file system structure includes a super block 302, one or more volume tables 310 and one or more Mode tables 320. The super block 302 is a root block representing the root of an aggregate 150; the super block is stored at predefined locations on disk 130 and comprises various system wide configuration data. The volume table 310 is a data structure having a plurality of entries 312. Illustratively, there is one entry 312 for every volume 140 in the aggregate, e.g., there is one entry for every snapshot of every volume, as well an entry for the active file system/volume. Each volume table entry 312 includes an Mode of a data structure, e.g., Mode table 320, which includes all other Modes of the volume.

In an illustrative embodiment, snapshots are generated at the volume level (i.e., on a per volume basis) although, in accordance with the on-disk structure described herein, snapshots can alternatively be generated at the Mode level (i.e., on a per file basis). It should be noted that the term “snapshot” is used for purposes of this patent to designate a persistent consistency point image. A persistent consistency point image (PCPI) is a space conservative, point-in-time read-only image of data accessible by name that provides a consistent image of that data (such as a storage system) at some previous time. More particularly, a PCPI is a point-in-time representation of a storage element, such as an active file system, file or database, stored on a storage device (e.g., on disk) or other persistent memory and having a name or other identifier that distinguishes it from other PCPIs taken at other points in time. A PCPI may comprise an active file system image that contains complete information about the file system, including all metadata. A PCPI can also include other information (metadata) about the active file system at the particular point in time for which the image is taken.

A multi-bit (e.g., 32-bit) monotonically increasing, snapshot identifier (“snapid”) is provided that represents a snapshot and that increases every time a snapshot is generated for a volume 140. The file system issues and allocates snapids sequentially per volume, thereby enabling the file system to accommodate a substantially large number of snapshots per volume. In addition, the snapid facilitates organization of snapshot metadata within, e.g., an indirect block or other data structure used to organize metadata associated with snapshot data, as described further herein. The snapid is also used to determine which blocks belong to which snapshots. To that end, every block that is used in a snapshot has an associated “valid-to” snapid denoting that the block is valid “up to” the snapshot identified by the snapid, after which the block is no longer valid.

For example, assume a first block is valid to snapshot (snapid) 10, a second block is valid to snapid 20, a third block is valid to snapid 30, and a fourth block is valid to snapid 40. Assume further that a request is issued to read data from a particular snapshot, e.g., snapid 35. In response, the data from the third block cannot be read because it was only valid up to snapid 30, but the fourth block is still valid and, as such, is the proper block to be accessed for that particular snapshot. Note that a block can reside in multiple snapshots; however the file system stores only one number (ID) for each block.

When generating a snapshot of a volume, the file system 300 allocates a new volume table entry 312 for that snapshot. Assume the snapid is 17 when a snapshot is generated. A new entry for the snapshot having a snapid 17 is allocated in the volume table 310 that points to the inode table 320 for that volume; accordingly, the snapshot (and allocated volume table entry) initially shares the inode table with the active file system. Thereafter, modifications are made to the active file system data within an active region of a file in the volume, as described below. As a result, the inode table 320 of the snapshot (snapid 17) starts to diverge from that of the active file system and, as a result, the snapshot forms its own inode table. However, the snapshot data remains intact in that region until a copy-out operation is performed to a snapshot region allocated to the file. Accordingly, each volume table entry 312 directly references (points to) the inode table 320 having a plurality of entries 322, each of which contains an inode identifying a file 400.

FIG. 4 is a schematic block diagram illustrating the on-disk structure of a file 400 that may be advantageously used in accordance with the present invention. Each file in the file system 300 has a hierarchical tree structure of metadata (indirect blocks) that is rooted at an inode 410 from an entry 322 of the inode table 320. The hierarchical tree structure illustratively has a fan-out that accommodates a large file by adding a level of indirection from among a plurality of, e.g., six, different indirect block trees. Illustratively, the inode 410 of the file 400 may contain, among other things, one or more level 0 pointers 412 that reference direct (L0) data blocks 420. In addition, the inode 410 may contain a level 1 pointer 414 that references a level one (L1) indirect block 700 of a first indirect block tree 430 that includes, e.g., a plurality of L0 blocks 420; a level 2 pointer 416 that references a level two (L2) indirect block 442 of a second indirect block tree 440 that may include a plurality of L1 indirect blocks 700 and L0 blocks 420; etc. up to a level 6 pointer 418 that references a level six (L6) indirect block (not shown) of a sixth indirect block tree 450 that eventually may include a plurality of L2 indirect blocks 442, as well as L1 indirect blocks 700 and L0 blocks 420.

The size of the indirect blocks is illustratively selectable, although each block pointer represents a predetermined (e.g., 64-bit) disk address. Depending upon the size of the file 400, the indirect block trees are filled, starting at the lowest indirect block tree level. For example, the first indirect block tree 430 can illustratively accommodate a file having up to 2000 blocks, the second indirect block tree 440 can accommodate a file having up to 4 million blocks and a third indirect block tree (not shown) can accommodate a file having up to 8 billion blocks. The structures of the indirect blocks (particularly above the L1 indirect block 700) are substantially similar, i.e., they include a list of pointers to other indirect blocks (at other levels). For instance, an L2 indirect block 442 may point to one or more L1 indirect blocks 700 or, in an alternate embodiment, may point to entire region 500 (that includes an L1 indirect block 700).

FIG. 5 is a schematic block diagram illustrating regions 500 of disk space that may be advantageously used with the present invention. The on-disk structure accommodates a plurality of types of regions 500, including (i) active regions 600 that contain active file system data for large files, (ii) snapshot regions 520 that contain “copy out” snapshot data for the large files and (iii) metadata regions 530 that contain metadata, as well as directories and small files. Illustratively, the regions are of equal size (e.g., 1 MB) and the size of the disk blocks, such as L0 blocks 420, is chosen to correlate with the size of the file blocks used by the file system. Furthermore, the file block size is variable, e.g., 4 kB, 8 kB, 128 kB, etc., and can be chosen to match the block size used by a client application 112 or desired by an administrator.

In an illustrative embodiment, the file system 300 allocates an active region 600 in response to an event, such as a request to create or extended a large file 400 in which to store data associated with the file. According to the on-disk structure, a first portion 620 of the active region 600 is used to store active file system data for the file 400 (i.e., active file data) and a second portion 640 is used to store snapshot data for the file. Illustratively, the first portion 620 of the active region 600 comprises a substantial amount (e.g., 80%) of the disk space of the region, while the second portion 640 comprises the remaining amount (e.g., 20%) of the region 600. For example, if the active region comprises 1 MB of disk space, then the first portion 620 of the region may comprise 800 kB of disk space or, if the file block size is 4 kB, approximately 200 file blocks. Instead of mapping each 800 kB portion of the file to 800 kB of disk space, the file system 300 maps the 800 kB of the file to a larger region of disk space, e.g., a 1 MB region of disk space. Illustratively, the disk space of a region appears on one disk but that is not a requirement of the on-disk structure; that is, the disk space of a region can be apportioned and striped across multiple disks 130.

Broadly stated, if an L2 indirect block 442 points to an entire region 500, then there are no snapshots and no L1 indirect blocks for the region. However, if an L2 indirect block 442 points to an L1 indirect block 700, then the indirect block 700 stores pointers to all active and snapshot blocks in the region. Illustratively, the L1 indirect block stores a pointer to the first portion 620 of the active region 600 used to store active file data and another pointer to the second portion 640 of the region used to store snapshot (copy-out) data. Keeping track of the snapshot copy-out portion 640 of an active region 600 allows the copied out data from the region to be stored contiguously. In addition, the L1 indirect block 700 stores an array of bits (e.g., a bit map), one per disk block, indicating whether the corresponding disk block has been copied out to a most recent snapshot, as described further herein.

Upon allocating, e.g., a first active region 600 a for the file, the file system 300 generally stores (writes) the active file data sequentially in allocated disk blocks of the first active file data portion 620 of that region. The file system is illustratively capable of writing any file block to any available disk block location within the active region 600. That is, the 800 kB of active file data may appear anywhere in the active region, not necessarily at the first 800 kB or last 800 kB of disk space, and not necessarily sorted in order. Subsequently, the file system 300 generates a snapshot and stores snapshot data associated with the file 400 in the second snapshot data portion 640 of the active region 600. Snapshot data is thus illustratively allocated on a per file basis within a region. The second portion 640 of the region may comprise the remaining 200 kB of disk space, e.g., 50 file blocks, which may also appear in any disk block location in the active region 600. Notably, the file system does not populate the second portion of the active region with active file data, but rather reserves that disk space for the snapshot data associated with the file. Over time, the file system 300 continues to populate the first portion 620 of the first active region 600 a with active file data of the large file 400 and the second portion 640 of the region with snapshot data of the file. Upon fully populating the first portion of the first active region with, e.g., 800 kB of active file data, the file system may allocate a second active region 600 b to store a next 800 kB of active file data for the file. Each active region 600 illustratively represents a contiguous space of file block numbers (fbns) from a file perspective.

The present invention is directed to an on-disk structure of a file system that has the capability to maintain snapshot and file system metadata on a storage system. According to the invention, the snapshot and file system metadata for a region is maintained within L1 indirect blocks of the on-disk structure. Each L1 indirect block 700 describes (i.e., represents) a corresponding region 500 of the on-disk structure of the file system; in the case of an active region 600, e.g., an L1 indirect block 700 represents the active file data portion 620 of a large file. That is, a first L1 indirect block represents the first 800 k bytes of the large file, a second L1 indirect block represents the next 800 k bytes of the file, etc. The L1 indirect block that references an active region also enables fbn-to-disk block number (dbn) mapping for the region. As a result, the L1 indirect block 700 is referred to as a “region indirect block” and is illustratively stored as the initial (root) block of its corresponding region 500. Storage of the region indirect block 700 within a corresponding region 500 is advantageous because most read and write operations require access (load/store) of the indirect block. In addition, storage of the indirect block 700 with the data of the region reduces disk head movement, thereby improving performance of the storage system.

Assume a block of the large file in the active region 600 has not been modified since a snapshot was generated, and now the file system 300 attempts to update the block with new active file data. However, assume further that the block is used in the previously generated snapshot and, thus, cannot be overwritten (i.e., must be maintained). As a result, the updated version of block is written to a new disk block location of an active region 600 allocated to the file 400, which new location is tracked (as part of the active file system) in the corresponding L1 indirect block 700. According to the invention, the L1 indirect block 700 keeps track of essentially all “accounting” information for the region, including whether a previous location of block is in the snapshot and must be maintained, thereby obviating the need for additional block allocation data structures, such as snapshot maps.

FIG. 6 is a schematic diagram illustrating the organization of an active region 600 that may be advantageously used with the present invention. In response to generation of a snapshot, some blocks within the first portion 620 of the active region 600 are marked as being used in the active file system (“active 622”), some blocks within the second portion 640 of the region are marked as being used in one or more snapshots (“snap 642”), and some blocks are marked as being unallocated (“free 662”). As the blocks that are marked “active 622” are overwritten with new active file data, e.g., in accordance with write operations, blocks marked “free 662” are used to store the new active file data. Over time, and as more snapshots are generated, the first and second portions of the region become fully populated such that there are no free blocks to accommodate subsequent write operations directed to file system data.

Referring again to FIG. 5, the file system 300 may allocate one or more snapshot regions 520 for the file, which region(s) is only used for storing snapshot data (i.e., copy-out data) that must be maintained for the snapshots. In an illustrative embodiment, a snapshot region 520 is allocated per file although, in an alternate embodiment, the on-disk structure may be extended to share snapshot regions among multiple files. The snapshot region 520 allocated to the file may hold snapshot data from any active region 600 allocated to the file. The file system 300 then invokes a copy-out process 350 that gathers all blocks of the active region 600 that are marked “snap 604”, including the blocks that are about to be overwritten, and writes the copy-out data of those blocks to the allocated snapshot region 520. As a result, the file may have a plurality of allocated regions, including active regions that contain active file system data and snapshot regions that contain snapshot data.

In an illustrative embodiment, the copy-out process 350 of the file system 300 gathers up the snapshot data, e.g., 200 kB or 50 blocks, from the first active region 600 a of the file and copies that data as a set to the snapshot region (e.g., a first snapshot region 520 a for the file). As a result, there are approximately 50 “free” blocks in the first active region 600 a that can be used for a next series of snapshots in that region. When those free blocks become populated with snapshot data, they are written to the first snapshot region 520 a, starting at a disk location where the previous set of snapshot data ended. Likewise, when the second active region 600 b becomes fully populated (e.g., 800 kB or 200 blocks of active file data and 200 kB or 50 blocks of snapshot data), the snapshot blocks are gathered and copied-out as a set to the first snapshot region 520 a of the file. Once the first snapshot region becomes fully populated with copy-out data, a second snapshot region 520 b is allocated to the file. Notably, there is some locality present among the sets of snapshot data stored in each snapshot region, since the region is populated with sets of, e.g., 50, snapshot blocks at a time. Accordingly, the copy-out data is not substantially fragmented over one or more disks 130, thereby improving sequential read operation performance for snapshots.

As noted, the L1 indirect block 700 keeps track of accounting information for its region; in the case of an active region 600, the L1 indirect block 700 keeps track of the contents of that region, including active file system data and snapshot data. When a copy-out operation is performed, the file system 300 updates metadata used to keep track of all snapshot data that has been copied out to a snapshot region 520 of a file. Illustratively, the file system 300 maintains a data structure, e.g., a B-tree structure, for each file that organizes the metadata associated with the copied-out snapshot data. Thus, according to the on-disk structure of the file system, each file 400 has an active tree structure comprising an inode and indirect blocks that reference data blocks configured to store active file data and snapshot data within an active region 600, as well as a B-tree structure that keeps track of all copied-out snapshot data for the file.

FIG. 7 is a schematic block diagram of the internal structure of an L1 indirect block 700 in accordance with the present invention. Each L1 indirect block 700 is configured to completely describe a region 500 of an aggregate 150 and, to that end, contains descriptive information of the region. For example, the L1 indirect block 700 has a base aggregate block number (ABN) field 710 that holds an identifier that uniquely identifies a is region in the aggregate 150. The identifier is illustratively a base ABN that references the region. Note that each region 500 of an aggregate 150 may be numbered sequentially or, as in the illustrative embodiment, may be assigned an address that expresses a byte position in the aggregate. In the latter case, the base ABN address 710 is a multi-bit (e.g., 64-bit) disk address of a first byte in a region of the aggregate.

A field 720 of the L1 indirect block 700 is organized as a data structure (e.g., a table) having a plurality of (e.g., 0-N) entries, each of which stores a region relative block number (RRBN 725). The entries of the RRBN table 720 essentially provide mappings between fbns and dbns within a region (e.g., the RRBN 725). RRBNs are employed because the active data of a file stored in the first portion 620 of an active region 600 is not necessarily contiguous. Note that the range of fbns for the active file data is stored in an indirect block tree (e.g., indirect block tree 800) and, as such, the position of an fbn in the indirect block tree specifies the location of the data in a file.

FIG. 8 is a schematic block diagram of an indirect block tree 800 that may be advantageously used with the present invention. Assume that an L2 indirect block 442 of indirect block tree 800 points to three L1 indirect blocks 700 a-c, wherein the first L1 indirect block 700 a is the first block of an active region 600 a whose active file data portion 620 a spans, e.g., approximately bytes 0 to 800 k in the aggregate 150, the second L1 indirect block 700 b is the first block of an active region 600 b whose active file data portion 620 b spans, e.g., approximately bytes 800 k to 1.6M in the aggregate and the third L1 indirect block 700 c is the first block of an active region 600 c whose active file data portion 620 c spans, e.g., approximately bytes 1.6M to 2.4M in the aggregate.

In response to a request to access an fbn stored at, e.g., approximately byte 900 k of the file, the file system 300 traverses the second L1 indirect block 700 b to access the appropriate region 600 b containing byte 900 k. The file system then determines that the fbn corresponding to byte 900 k is, e.g., 100 entries into the mapping table 720 and, thus, indexes into entry 100 to retrieve a RRBN 725. Illustratively, the RRBN is a multi-bit (e.g., 16-bit) number that can accommodate regions up to 64 k blocks, although the example used herein requires addressing of only lk blocks. Armed with a base ABN address 710 of the region 600 b (e.g., 800 k), the file system 300 determines that the fbn corresponding to byte 900 k is 100 k bytes into the region. The corresponding RRBN 725 is an on-disk block number (dbn) that is relative to the base ABN address 710 of that region and, as such, indicates the location of the block on disk. Essentially, the on-disk structure of the file system 300 involves indexing into a predetermined multi-bit (e.g., 64-bit) disk address space using a first multi-bit (64-bit) address, i.e., the base ABN address 710, and then using a smaller second multi-bit (e.g., 16-bit) address for every block (i.e., the RRBN 725), rather than requiring the larger first multi-bit (e.g., 64-bit) address per block, which would be expensive.

The L1 indirect block 700 also has a field 730 that stores a value indicative of the next snapshot to be taken at a point in time when any block in its active region 600 was last written, i.e., a “region snapid 730”. Storage of the region snapid 730 in the indirect block 700 ensures that, when a snapshot is taken, the file system 300 does not need to update the content of every indirect block. Note that file system 300 maintains an additional value, i.e., a “volume snapid” 330, adapted to keep track of the next snapshot to be taken when any block in the entire volume 140 was last written.

A field 740 of the L1 indirect block 700 is organized as a data structure that stores information pertaining to fbns that have been overwritten since the last snapshot. The data structure is illustratively embodied as a bit map 740 containing a plurality of (e.g., 800) bits representing a range of (e.g., 800) file blocks and that identifies those fbns within the range that have been overwritten since the last snapshot (identified by the region snapid 730). That is, the L1 indirect block 700 stores an array of bits, one per disk block, indicating whether the corresponding disk block has been copied out to a most recent snapshot. Note that the snapshot identified by the region snapid 730 may not be the last snapshot taken of the volume, but rather identifies the last snapshot taken when any block of the region 600 was changed.

Notably, when the values of the region snapid 730 and volume snapid 330 match, the bit map 740 is valid. If the volume snapid 330 is greater than the region snapid 730, then no blocks in the region 600 were modified (written) since the last snapshot of the volume was taken and the bit map 740 is invalid and, thus, ignored. Accordingly, the bit map 740 is only valid in the interval between the point when a block is written in the active region 600 and the region snapid 730 (and volume snapid 330) are updated, and the point at which only another region 600 of the volume is written 140 and the volume snapid 330 is updated.

In an illustrative embodiment, the bit map 740 is used to determine whether or not to keep a block that is overwritten. For example, an unasserted (e.g., zero) bit of the bit map 740 may denote that the corresponding block has not yet been overwritten, but that the block is in a snapshot and, therefore, the file system 300 should maintain that block. On the other hand, an asserted (e.g., one) bit may denote that the corresponding block has been overwritten since the last snapshot and that the file system 300 can overwrite it again because its previous “old” data is not preserved in a snapshot. Once a new snapshot is taken of the volume 140, changing the volume snapid 330 logically (and instantly) clears all bit maps 740 in all L1 indirect blocks 700 in an atomic manner, which is efficient because the file system does not have to “touch” (individually process) any of those indirect blocks.

The L1 indirect block 700 also includes a field 750 organized as a data structure that illustratively records (marks) the use of each disk block in the active file system and/or snapshot of an active region 600. The data structure is a “snap cache” structure 750 illustratively embodied as a table having a plurality of entries 760, each of which records a value indicating a count (e.g., 0-N) of used (allocated) entries of the table. For example, every time a block is overwritten, an entry 760 is created in the snap cache 750 and the count of allocated entries is incremented. The count keeps incrementing with subsequent overwritten blocks until either the snap cache table 750 is filled or the active region 600 is filled, at which point a copy-out operation of the snapshot data is performed.

In the illustrative embodiment, each entry 760 in the table 750 has three (3) subfields: (i) a first sub-field that holds an fbn 762, (ii) a second sub-field that holds a RRBN 725 and (iii) a third sub-field that holds a snapid 766. The entries 760 of the snap cache table 750 pertain to blocks that only appear in snapshots (i.e., that are no longer active), but that are still in the region 600. For example, when a block is overwritten in an active region but is still in a snapshot, an entry 760 is created in the snap cache 750 that contains (i) the fbn 762 of the block, (ii) the RRBN 725 of the block (obtained via the mapping table 720) and (iii) the snapid 766 up to which the block is valid (i.e., “valid-to-snapid”). The valid-to-snapid 766 is illustratively the region snapid 730 (stored in the L1 indirect block 700), which is also stored in the snap cache table 750 because the contents of the table are maintained until the region is fully populated or until the snap cache table is fully populated.

The snap cache table 750 can be configured as large as needed but, in the illustrative embodiment, is configured with at least 50 entries to record at least 50 snapshot blocks to thereby accommodate the 50 blocks in the second portion 640 of an active region 600 (i.e., the remaining 200 kB of disk space) that contain snapshot data. Once the snapshot data is copied out of an active region and the entire L1 indirect block 700 is rewritten, the snap cache 750 is cleared. Specifically, all of the accounting information in the snap cache 750 is transferred to the B-tree, which describes all of the copied out data.

While there have been shown and described illustrative embodiments of an on-disk structure of a file system that has the capability to maintain snapshot and file system metadata on a storage system, it is to be understood that various other adaptations and modifications may be made within the spirit and scope of the present invention. For example, it will be understood to those skilled in the art that the sizes of the multi-bit identifiers (e.g., snapid), addresses (e.g., base ABN address, disk address space), and block numbers (e.g., RRBN) can vary to accommodate various sizes of identifiers, addresses/address spaces, block numbers and regions and that the examples used herein are employed solely for illustrative purposes.

The foregoing description has been directed to specific embodiments of this invention. It will be apparent, however, that other variations and modifications may be made to the described embodiments, with the attainment of some or all of their advantages. For instance, it is expressly contemplated that the components and/or structures described herein can be implemented as software, including a computer-readable medium having program instructions executing on a computer, hardware, firmware, or a combination thereof. Also, electromagnetic signals may be generated to carry computer executable instructions that implement aspects of the present invention over, e.g., a wireless data link or a data network, such as the Internet. Accordingly this description is to be taken only by way of example and not to otherwise limit the scope of the invention. Therefore, it is the object of the appended claims to cover all such variations and modifications as come within the true spirit and scope of the invention. 

What is claimed is:
 1. A system, comprising: a storage operating system executing on a storage system having a processor and configured to generate snapshots of file system data associated with at least one data container; and an on-disk structure of a file system of the storage system, the on-disk structure configured to apportion storage space of storage devices into a plurality of regions, wherein each region of the plurality of regions stores the file system data and the snapshot data associated with a different sequential portion of the at least one data container, and wherein a level one (L1) indirect block is stored as an initial block within the region and maintains metadata describing the file system data and snapshot data stored in the region, the region associated with the different sequential portion of the at least one data container; and the storage operating system further configured to receive a write operation directed to the block wherein the write operation is associated with a new version of the block, and write the new version of the block to a free block in the region based on the indirect block indicating that the previous version of the block in the region is utilized in the snapshot and is maintained and not overwritten.
 2. The system of claim 1 wherein the region includes an active region that stores the file system data.
 3. The system of claim 1 wherein the L1 indirect block comprises a base aggregate block number (ABN) identifier.
 4. The system of claim 1 wherein the storage operating system is further configured to enable a file block number (fbn) to disk block number (dbn) mapping by the indirect block for the region. 